These benchmarks exist to show why the APIs are forbidden

…race-java into dougqh/strings-improvements

…tion)

Per bric3 review: the doc said what SubSequence avoids allocating but not why it
matters. Explain the use case — allocation-free lightweight parsing: substring/
subSequence copy per call, so splitting a string into many pieces on a hot path
allocates O(pieces) Strings; SubSequence is a zero-copy view. Also fixes a typo.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…ovements

SharedDBCommenter.containsTraceComment built nine "KEY + =" strings on every
call: the keys are encode()-derived (not compile-time constants), so each
"KEY + =" is a runtime concat. A non-matching comment ran all nine checks and
allocated nine throwaway Strings per call. Precompute the needles once at class
init as *_EQ constants; the contains-chain is unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Throughput benchmark at @threads(8) over a realistic comment-content mix
(mostly non-DD, the all-nine-checks worst case) to surface the per-call
allocation removed by hoisting the "<key>=" needles to constants. Run the
parent commit (baseline) vs this branch and read the ops/s delta; -prof gc
(gc.alloc.rate.norm) corroborates the mechanism.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…tent substring

SQLCommenter.hasDDComment materialized sql.substring(commentStart, commentEnd)
on every duplicate-comment check just to feed containsTraceComment. Add a
SharedDBCommenter.containsTraceComment(sql, from, to) range overload that scans
the comment body in place, and a Strings.regionContains primitive it (and the
String delegate) build on -- no per-call substring. The String overload now
delegates to the range form, so Mongo behavior is unchanged.

regionContains is the allocation-free, copy-free primitive; the natural-reading
SubSequence.contains layer can delegate to it later. Boundary semantics unit-
tested on Strings.regionContains; DB needle behavior on the overloads; existing
SQLCommenter/SharedDBCommenter suites unchanged and green.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…o dougqh/dbcommenter-scan-overload

# Conflicts:
#	internal-api/src/main/java/datadog/trace/util/Strings.java

…diom)

Add SubSequence.contains (delegating to the Strings.regionContains primitive)
and rewrite containsTraceComment(sql, from, to) as
SubSequence.of(sql, from, to).contains(...) -- a 1-to-1 substitution for what
you'd idiomatically write on a substring, with no copy. EA elides the view in
the transient consumption; even if it doesn't, the string copy is still avoided.

Couples this branch to the SubSequence base (#10640); regionContains stays as
the allocation-free primitive the view delegates to.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Isolates the duplicate-comment guard (dbType=null skips the first-word scan;
already-DD-commented SQL makes inject return early). The extractCommentContent
substring allocated 140 B/op; the in-place range/view scan is EA-elided (~0).
@threads(8), @fork(2), -prof gc; numbers in the class Javadoc. Throughput is
flat-to-slightly-up but within @fork(2) noise -- this path is scan-CPU-dominated,
so the win is the allocation, not throughput.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>